Fix ngStrictDi support #3479
Merged
Fix ngStrictDi support #3479
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some scenarios, the `$injector` would be asked to annotate without providing it with the current `strictDi` value, making resolvables not complain about missing annotations.
|
Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some scenarios, the
$injectorwould be asked to annotate withoutproviding it with the current
strictDivalue, making resolvables notcomplain about missing annotations.
This was previously addressed in this PR: #2602
Yet, it is not working, as can be seen in this plunker, that contains a resolvable without annotations and yet no error is thrown: http://plnkr.co/edit/dd6ptmrUtzPnKLmAJkCY?p=preview